Skip to content

fix(windows): reap republished daemons during nuke#657

Open
nsxdavid wants to merge 1 commit into
justrach:release/0.2.5829from
nsxdavid:fix/windows-nuke-reap-daemons
Open

fix(windows): reap republished daemons during nuke#657
nsxdavid wants to merge 1 commit into
justrach:release/0.2.5829from
nsxdavid:fix/windows-nuke-reap-daemons

Conversation

@nsxdavid

@nsxdavid nsxdavid commented Jul 4, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Follow-up to merged Add Windows warm daemon IPC #641 for the Windows nuke cleanup path.
  • Reap metadata-discovered Windows warm daemons in bounded passes so retry-mode serve/mcp daemons that republish cli-daemon.pipe after the visible owner exits are also terminated.
  • Keep cleanup scoped to cli-daemon.pipe records under {home}/.codedb/projects and retain process-image verification before termination.

Issue

No standalone issue exists; this addresses the post-merge Codex review note about multiple retry-mode Windows daemons.

Validation

  • zig build --global-cache-dir .zig-global-cache test-mcp -Dtest-filter="nuke" --summary all - 7/7 tests passed
  • zig build --global-cache-dir .zig-global-cache test --summary all - 869/873 tests passed (4 skipped)
  • zig build --global-cache-dir .zig-global-cache --summary all - 3/3 steps succeeded
  • PYTHONUTF8=1; python scripts/e2e_mcp_test.py --binary zig-out/bin/codedb.exe --project . - 20/20 passed on Windows using a repo-local test home
  • git diff --check - passed

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 989f8eaf45

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread src/nuke.zig Outdated
@nsxdavid nsxdavid force-pushed the fix/windows-nuke-reap-daemons branch 2 times, most recently from 18d898d to bc4f46a Compare July 4, 2026 23:40
@nsxdavid nsxdavid force-pushed the fix/windows-nuke-reap-daemons branch from bc4f46a to cfde602 Compare July 12, 2026 19:59
@nsxdavid nsxdavid changed the base branch from release/0.2.5828 to main July 12, 2026 19:59
@github-actions

Copy link
Copy Markdown

👋 Thanks for the contribution! Quick heads-up: this repo lands changes on the current release/* branch, not main.

Please retarget this PR via Edit → base branch to the active release/* branch shown in the repository branch list.

(Automated hint — reply here if you need a hand.)

@nsxdavid

nsxdavid commented Jul 12, 2026

Copy link
Copy Markdown
Contributor Author

Rebased onto the active release/0.2.5829 line and retargeted this PR accordingly. This remains a Windows-specific nuke cleanup fix; the later POSIX socket-handover work does not cover it. Fresh Windows validation with Zig 0.17.0-dev.813+2153f8143: nuke tests passed; full suite 23/23 build steps; normal build 3/3; MCP E2E 20/20.

@nsxdavid nsxdavid force-pushed the fix/windows-nuke-reap-daemons branch from cfde602 to 9bf5148 Compare July 13, 2026 02:22
@nsxdavid nsxdavid changed the base branch from main to release/0.2.5829 July 13, 2026 02:22
@nsxdavid

Copy link
Copy Markdown
Contributor Author

Corrected per the repository guard: this PR now targets release/0.2.5829, the active release line. I replayed only the Windows nuke fix as 9bf5148 and revalidated that exact branch with Zig 0.17.0-dev.813+2153f8143: nuke gate passed; full suite 23/23 build steps; normal build 3/3; MCP E2E 20/20.

@nsxdavid

Copy link
Copy Markdown
Contributor Author

CI note: the new bench run stops before compilation because the release workflow cannot download its repository-pinned Zig archive (zig-x86_64-linux-0.17.0-dev.813+2153f8143.tar.xz returns HTTP 404). This is a workflow/toolchain availability issue on the base branch, not a benchmark regression from this one-file fix. The exact pinned compiler completed the local Windows validation above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant